Session management apparatus, user plane apparatus, and access mobile management apparatus

ABSTRACT

A session management apparatus including: a reception unit configured to receive, from a user plane apparatus, a time offset between a TSN time of a TSN time domain and a 5G time, and identification information of the TSN time domain; and a transmission unit configured to transmit, to a base station apparatus, a TSC assistance information determined based on the time offset and the identification information of the TSN time domain.

TECHNICAL FIELD

The present invention relates to network apparatuses in a communication system.

BACKGROUND ART

In the 3rd Generation Partnership (3rd GPP) project, a wireless communication system called 5G or NR (hereinafter, the wireless communication system is referred to as “5G” or “NR”) is being studied in order to achieve further increase in system capacity, further increase in data transmission speed, and further decrease in the delay in the wireless section. In 5G, various wireless technologies are being studied in order to achieve a throughput of 10 Gbps or higher and to meet the requirement of a delay of 1 ms or less in the wireless section.

In 5G, a network architecture that includes 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core), which is the core network in the LTE (Long Term Evolution) network architecture, and NG-RAN (Next Generation Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the LTE network architecture, is under consideration. In some cases, NG-RAN is referred to as 5G-AN, RAN, or gNB.

In recent years, there has been an increase in the demand for synchronous control of a large number of devices in factories, etc., and a standard for synchronous communication (IEEE P802.1Qcc, etc.) that enables such control has been specified.

In the 5G system, TSC (Time Sensitive Communication) specified in IEEE P802.1Qcc is also supported (Non-Patent Document 1). In the TSC, the 5G system functions as a TSN (Time Sensitive Networking) bridge.

In addition, TSC support information (TSC Assistance Information) describing TSC traffic characteristics is provided by SMF to NG-RAN. The gNB, which is NG-RAN, is able to understand a TSN traffic pattern and perform efficient schedule, etc. by TSCAI.

PRIOR ART DOCUMENTS Non-Patent Documents

-   [Non-Patent Document 1] 3GPP TS 23.501 V16.1.0 (2019 June) -   [Non-Patent Document 2] 3GPP TS 23.502 V16.1.1 (2019 June) -   [Non-Patent Document 3] 3GPP TS 29.244 V16.0.0 (2019 June) -   [Non-Patent Document 4] 3GPP TS 29.518 V15.4.0 (2019 June) -   [Non-Patent Document 5] 3GPP TS 38.413 V15.4.0 (2019 July) -   [Non-Patent Document 6] 3GPP TS 38.415 V15.2.0 (2018 December)

SUMMARY OF INVENTION Problem to be Solved by the Invention

As described in Non-Patent Document 1, when a drift occurs between a TSN time and a 5G time in a TSN time domain, the core NW notifies NG-RAN of a modified TSCAI parameter. The TSN time domain may also be referred to as a “time domain”.

Although the 5G system supports multiple TSN time domains (TSN working domain), the above modified TSCAI parameter needs to be applied only to the TSN time domain in which the drift occurs and not to other TSN time domains in which no drift occurs. However, since gPTP messages of multiple TSN time domains belong to a single QoS flow, the prior art cannot apply the modified TSCAI parameter only to the TSN time domain in which the drift occurs.

The present invention has been developed in view of the foregoing, and is intended to provide a technique that enables TSC assistance information to be applied only to a specific TSN time domain.

Means for Solving Problems

According to the disclosed technique, there is provided A session management apparatus comprising:

-   -   a reception unit configured to receive, from a user plane         apparatus, a time offset between a TSN time of a TSN time domain         and a 5G time, and identification information of the TSN time         domain; and     -   a transmission unit configured to transmit, to a base station         apparatus, a TSC assistance information determined based on the         time offset and the identification information of the TSN time         domain.

Effects of the Invention

According to the disclosed technique, there is provided a technique that allows TSC assistance information to be applied only to a specific TSN time domain.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram for explaining a communication system according to an embodiment of the present invention;

FIG. 2 is a diagram showing a system configuration of TSN Time Synchronization.

FIG. 3 is a diagram showing a TSN bridge.

FIG. 4 is a diagram for explaining an operation in a TSN bridge.

FIG. 5 is a diagram for explaining an operation in a TSN bridge.

FIG. 6 is a diagram showing TSC Assistance Information.

FIG. 7 is a diagram for explaining a processing sequence.

FIG. 8 is a diagram showing an example of changes to the specification (T523.501).

FIG. 9 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 10 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 11 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 12 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 13 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 14 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 15 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 16 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 17 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 18 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 19 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 20 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 21 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 22 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 23 is a diagram showing an example of a change to the specification (TS29.244).

FIG. 24 is a diagram showing an example of changes to the specification (TS23.502).

FIG. 25 is a diagram showing an example of changes to the specification (TS23.502).

FIG. 26 is a diagram showing an example of changes to the specification (TS23.502).

FIG. 27 is a diagram showing an example of changes to the specification (TS38.413).

FIG. 28 is a diagram showing an example of changes to the specification (TS38.413).

FIG. 29 is a diagram showing an example of changes to the specification (TS38.413).

FIG. 30 is a diagram showing an example of changes to the specification (TS38.413).

FIG. 31 is a diagram showing an example of changes to the specification (TS38.413).

FIG. 32 is a diagram showing an example of changes to the specification (TS38.413).

FIG. 33 is a diagram showing an example of changes to the specification (TS38.413).

FIG. 34 is a diagram showing an example of changes to the specification (TS38.415).

FIG. 35 is a diagram showing an example of changes to the specification (TS38.415).

FIG. 36 is a diagram showing an example of changes to the specification (TS38.415).

FIG. 37 is a diagram showing an example of a functional configuration of the base station apparatus 30 according to an embodiment of the present invention.

FIG. 38 is a diagram showing an example of a functional configuration of the AMF 20 according to an embodiment of the present invention;

FIG. 39 is a diagram showing an example of a functional configuration of the SMF 40 according to an embodiment of the present invention;

FIG. 40 is a diagram showing an example of a functional configuration of the UPF 50 according to an embodiment of the present invention;

FIG. 41 is a diagram illustrating an example of the hardware configuration of the base station apparatus 30, the AMF 20, the SMF 40, and the UPF 50 according to an embodiment of the present invention;

MODE FOR CARRYING OUT THE INVENTION

Hereinafter, embodiments of the present invention will be described with reference to the drawings. The embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to the following embodiments.

In operating the communication system according to an embodiment of the present invention, existing techniques may be used, as appropriate. The existing technology is, for example, an existing LTE or existing 5G, but is not limited to an existing LTE or existing 5G.

In the following description, the node name, signal name, etc. currently described in the 5G specification (or the LTE specification) are used. However, the node name, signal name, etc. having the same function may be called by a different name.

(Example of System Configuration)

FIG. 1 is a diagram illustrating a communication system (may be referred to as a communication network) according to an embodiment of the present invention. As shown in FIG. 1, the communication system comprises a UE 10 (which may be referred to as a user equipment 10 or terminal 10), and a plurality of network nodes. Hereinafter, one network node corresponds to each function, but multiple functions may be realized by one network node or multiple network nodes may realize one function. Also, “connection” described below may be a logical connection or a physical connection.

In FIG. 1, each of the UPF 50, the AMF 20, and the SMF 40 is an example of a network node (also referred to as a network apparatus) that constitutes a core network of a communication system (here, 5G). Communication between the RAN 30 and the UPF 50 is performed via the core network.

RAN (Radio Access Network) 30 is a network node with wireless access functions, and is connected to the UE 10, the AMF (Access and Mobility Management Function) 20 and the UPF (User plane function) 50. The RAN 30 may also be referred to as a gNB 30 or a base station apparatus 30.

The AMF 20 is a network node having functions such as a RAN interface termination, a NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The AMF 20 may also be referred to as an access mobility management apparatus.

The UPF 50 is a network node having functions such as a PDU (Protocol Data Unit) session point for an external entity interconnecting with a DN (Data Network), packet routing and forwarding, and QoS (Quality of Service) handling on the user plane. The UPF 50 transmits and receives user data. The UPF 50 and the DN constitute network slices. In the communication network according to an embodiment of the present invention, a plurality of network slices are formed.

In the example of FIG. 1, one UPF 50 corresponds to one network slice. However, one UPF 50 may operate multiple network slices. The UPF 50 may also be referred to as a user plane apparatus.

The UPF 50 is physically, for example, one or more computers (servers, etc.). A plurality of resources that can logically integrate and divide hardware resources (CPU, memory, hard disk, network interface, etc.) of the computer can be regarded as resource pools, and each resource can be used as a network slice in the resource pool. When the UPF 50 operates a network slice, for example, it manages correspondence between a network slice and a resource, starts and stops the resource, and monitors operational status of the resource, and so on.

The AMF 20 is connected to the UE 10, the RAN 30, the SMF (Session Management function) 40, a NSSF (Network Slice Selection Function), a NEF (Network Exposure Function), a NRF (Network Repository Function), an AUSF (Authentication Server Function), a PCF (Policy Control Function), and an AF (Application Function). The AMF, the SMF, the NSSF, the NEF, the NRF, the AUSF, the PCF, and the AF are interconnected network nodes via their respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nausf, Npcf, and Naf.

The SMF 40 is a network node having functions such as session management, Internet Protocol (IP) address assignment and management of UE, DHCP (DHCP) function, Address Resolution Protocol (ARP) proxy, and roaming function, and the like. The SMF 40 may also be referred to as a session management apparatus.

The NEF is a network node that has a function to notify other NFs (Network Functions) of capabilities and events. The NSSF is a network node that has functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining a NSSAI to be configured, and determining an AMF set to which the UE connects. The PCF is a network node having a function for controlling a policy of the network. The AF is a network node that has a function of controlling an application server.

(Basic Operation)

The communication system (5G system) in accordance with this embodiment supports TSN time synchronization as shown in FIG. 2 (FIG. 5.27.1-1 of Non-Patent Document 1). A 5G system that supports TSN time synchronization corresponds to “time aware system” in IEEE 802.1AS. In the 5G system, only the TSN translator (TT) at its edge supports the operation of IEEE 802.1AS, and a UE, a gNB, a UPF, a NW-TT (Network-side TSN translator), and a DS-TT (Device-side TSN translator) are synchronized to 5G GM (5G internal system clock).

As shown in FIG. 3 (FIG. 4.4.8.2-1, Non-Patent Document 1), the 5G system functions as a TSN bridge. FIG. 3 shows a TSN AF which is an application node related to TSN.

Referring to FIG. 4, an example of a method for distributing a TSN clock will be described. Delivery of TSN clocks uses gPTP messages. A gPTP message includes a precession origin timestamp at the time when the gPTP message is sent, a correction field, and so on.

A gPTP message sent from a TSN end station or the like in a TSN time domain is received by the UPF 50 and an ingress time stamp (TSi) is added to the gPTP message by the NW-TT in the UPF 50. The NW-TT may be a function in the UPF 50 or may be a function outside the UPF 50.

The gPTP message is sent to the UE 10 using a PDU session for the UE 10 communication. The UE 10 transmits the received gPTP message to the DS-TT, and the DS-TT generates an egress time stamp (TSe) for the gPTP message, and calculates a residence time of the gPTP message in the 5G system as “TSe-TSi”. The DS-TT strores the residence time in the correction field of the gPTP message and transmits it to the TSN end station and the like. The DS-TT may be a function in the UE 10 or may be a function outside the UE 10.

Regardless of the number of TSN time domains, a single PDU session is used per one UPF and per one UE for transmitting the gPTP message. FIG. 5 shows an example where gPTP messages for two TSN time domains are transmitted in one PDU session. Since the gPTP message contains a domain number to identify a TSN time domain, the end station receiving the gPTP message can identify a TSN time domain of the gPTP message by the domain number.

Delivery of the TSN clock and the timestamp described above is performed between the UE 10 and the UPF 50 for each TSN time domain. If the UE 10 is connected to multiple TSN time domains via a single UPF 50, the gPTP messages of all TSN time domains are transmitted to the UE 10 by the same single PDU session.

(About TSCAI)

For example, when establishing a QoS flow, a TSCAI (TSC Assistance Information) describing TSC traffic characteristics is provided to the RAN 30 from the SMF 40 via the AMF 20. The gNB that is the RAN 30 according to this embodiment can understand the TSN traffic pattern and perform efficient scheduling by TSCAI.

The SMF 40 determines TSCAI parameters based on information obtained, for example, from a TSN AF. The SMF 40 may determine the TSCAI parameters based on information (such as offsets) reported from the UPF 50.

FIG. 6 (Table 5.27.2-1 of Non-Patent Document 1) shows an example of TSCAI. As shown in FIG. 6, TSCAI includes Flow Direction, Periodicity, and Burst Arrival Time. Flow Direction indicates whether a target TSC flow is uplink or downlink. Periodicity indicates a time interval (period) between two bursts in a series of traffic. The Burst Arrival Time (burst arrival time) indicates the time of arrival of the first data burst of a series of traffic to the RAN 30 in uplink or downlink. A reference of the Burst Arrival Time is a 5G clock, and the SMF 40 maps the Burst Arrival Time from the TSN clock that is a reference of the TSN stream to the 5G clock. The TSN AF may perform this mapping.

For example, in a TSN time domain, assuming that the time of the 5G clock (e.g., a clock provided by the UPF 50) is advanced by ΔT with respect to the time of the TSN clock (e.g., a clock provided by the TSN end station). At this time, assuming that the Burst Arrival Time in the TSN clock is T, the SMF 40 calculates the Burst Arrival Time in the 5G clock as T+ΔT.

If a drift (change of ΔT) occurs between a TSN time (TSN time) in a TSN time domain and a 5G time (5G time), the UPF 50 notifies the SMF 40 of an offset and the SMF 40 notifies the RAN 30 of a TSCAI parameter modified based on the offset. The TSCAI parameter here is, for example, Burst Arrival Time, but is not limited to Burst Arrival Time. Also, “offset” is the difference (corrected ΔT) between TSN time and 5G time, but is not limited thereto. For example, the “offset” may be the amount of deviation from the ΔT before modification.

As noted above, if the UE 10 is connected to multiple TSN time domains via a single UPF 50, the gPTP messages of all TSN time domains are transmitted to the UE 10 by the same single PDU session. Since there is no reason to treat each of these multiple TSN time domains as different QoS, in practice, it is assumed that gPTP messages for all these TSN time domains will be transmitted in a single QoS flow.

The above modified TSCAI parameter needs to be applied only to the TSN time domain in which the drift occurred. However, since gPTP messages of multiple TSN time domains belong to a single QoS flow, the prior art cannot apply the modified TSCAI parameter only to the TSN time domain in which the drift occurred.

In this embodiment, in order to solve the above-described problem, the configuration of the TSCAI can be set for each QoS flow+TSN time number (identification information of the time domain) on N2, and the TSN time number can be set for the PDU Session user plan protocol on N3. Hereinafter, this technique will be described in detail as an example.

Example

FIG. 7 shows an example of a processing flow in the present embodiment. In S101, the SMF 40 transmits a message to the UPF 50 requesting offset reporting. This message may be, for example, a PFCP Session Establishment Request at the time of establishing a PDU session or a PFCP Session Modification Request at the time of modifying a PDU session. But, the message is not limited to these. The UPF 50 may, at its own discretion, report the offset to the SMF 40 without making a request of S101.

In the following description, offset reporting at the time of drift detection is described. However, this is an example. The UPF 50 may report the offset for each TSN time domain detected in the corresponding PDU session, even in the absence of drift detection.

In S102, the UPF 50 detects drift between TSN time and 5G time in a TSN time domain in a corresponding PDU session for the UE 10. Any method can be used for detecting a drift. For example, the UPF 50 may detect a drift by change of a difference between a time stamp provided by the NW-TT in the gPTP message of the TSN time domain and the TSN source time stamp, may detect a drift based on information from the TSN AF, or may detect a drift by other methods.

In S103, the UPF 50 acquires the number (domain number) of the TSN time domain in which the drift is detected from the gPTP message and transmits the message including the domain number and the offset to the SMF 40. This message is for example a PFCP Session Report Request. The domain number is extracted from the relevant gPTP message.

The SMF 40 that received the message determines a TSCAI parameter (e.g., Burst Arrival Time) based on the offset (this “determine” also includes “update”), and transmits the message containing the TSCAI parameter and domain number to the AMF 20 at S104. This transmission is performed, for example, by step 3b (Namf_Communication_N1N2MessageTransfer) of PDU session modification (Non-Patent Document 2, FIG. 4.3.3.2-1).

In S105, the AMF 20 transmits a message to the RAN 30 containing the domain number and the TSCAI parameter (e.g., Burst Arrival Time). This transmission is performed, for example, by step 4 (N2 PDU Session Request) of the PDU session modification (Non-Patent Document 2, FIG. 4.3.3.2-1).

It is assumed that, based on the TSCAI received before the execution of S105 shown in FIG. 7, a control unit of the RAN 30 prepares (allocates) a time slot so that the RAN 30 transmits data of Burst Arrival Time=T, period P, and size S per period in a TSN time domain to the UE 10 or the UPF 50 by a QoS flow in a PDU session. At this time, if the RAN 30 receives Burst Arrival Time=T+ΔD with respect to the TSN time domain in S105 of FIG. 7, the control unit of the RAN 30 allocates a time slot by shifting the start of the time slot to T+ΔD for the TSN time domain.

“Allocate” means to reserve the time slot for transmission of the Burst data. When the Burst data arrives from the UPF 50 or the UE 10, the transmission unit of the RAN 30 transmits the Burst data to the UE 10 or the UPF 50 in the reserved time slot.

(Example of Change in Specification)

The following is an example of changes to the specifications (specifications) corresponding to the above-mentioned flow. The communication system of the present embodiment operates in accordance with the modified specification.

FIG. 8 shows a change from Non-Patent Document 1 (extract of T538.501). “To address each individual drift between each TSN time and 5G time when supporting the multiple TSN working domains, the TSCAI parameter needs to be differentiated based on the TSN working domain. This needs to apply also to the case when gPTP messages from those domains are forwarded via the same QoS flow in the same PDU session.”, it is defined that, when a plurality of TSN time domains are supported, the TSCAI parameter is determined for each TSN time domain.

FIGS. 9-23 are examples of specification modifications of portions corresponding to S101 and S102 of FIG. 7 and show modifications from Non-Patent Document (extract of TS29.244).

FIG. 9 defines Reporting of the offset between TSN time and 5G time to the SMF. In a PFCP Session Establishment Request or PFCP Session Modification Request, the SMF 40 can request the UPF 50 to start or stop reporting the offset between TSN time and 5G time. The UPF 50 that receives a request for reporting reports, for example, the offset values of all domain numbers that detected a drift, together with the corresponding domain numbers, to the SMF 40 by a PFCP Session Report Procedure. The details are as shown in FIG. 9.

FIG. 10 shows details of the information elements of the PFCP Session Establishment Request, with Create PTR added. FIG. 11 shows details of the Create PDR IE in which PTR ID is added. FIG. 12 shows Ethernet Packet Filter IE within PFCP Session Establishment Request, in which EtherType is added. This EtherType IE is a key for the UPF 50 to perform DPI for detecting a value or a field of a gPTP message. FIG. 13 shows details of Create PTR IE within PFCP Session Establishment Request.

FIG. 14 shows information elements of the PFCP Session Modification Request, in which Remove PTR, Create PTR, and Update PTR are added. FIG. 15 shows details of Update PDR IE within PFCP Session Modification Request in which PTR ID is added. FIG. 16 shows details of the Update PTR IE and FIG. 17 shows details of the Remove PTR IE.

FIG. 18 shows information elements of the PFCP Session Report Request in which PTR Report is added. FIG. 19 shows details of the PTR Report IE, which defines reporting the pair of domain number and offset as time offset information. FIGS. 20-23 show details of Report Type, EtherType, PTR ID, PTR Reporting Triggers, Domain Number, Time Offset.

FIGS. 24-26 show changes from Non-Patent Document 2 (abstract of T523.502). FIG. 24 shows modification of Non-Patent Document 2, 4.3.2.2.1, showing modification of step 10a of UE-requested PDU Session Establishment as shown in FIG. 4.3.2.2.1-1. As shown in FIG. 24, when SMF 40 determines to use TSCAI in a PDU session, the SMF 40 includes rules for drift detection into N4 Session Establishment/Modification Request.

FIG. 25 is a modification of step 1d of the UE or network requested PDU Session Modification shown in FIG. 4.3.3.2-1 of Non-Patent Document 2. As described in FIG. 25, the SMF requested modification is triggered when TSCAI is updated.

FIG. 26 is a change of step 2a of UE or network requested PDU Session Modification shown in FIG. 4.3.3.2-1 of Non-Patent Document 2. When SMF 40 determines that TSCAI is used in the PDU session, the N4 Session Establishment/Modification Request includes rules for drift detection.

For notifying a domain number and a TSCAI parameter from the SMF 40 to the AMF 20, for example, the N1N2MessageTransfer shown in step 11 of FIG. 4.3.2.2.1-(UE-requested PDU Session Establishment) of Non-Patent Document 2 (T523.502) and step 3b of FIG. 4.3.3.2-1 (UE or network requested PDU Session Modification) is used. Specifically, the N1N2MessageTransferRefData, which includes the domain number and the TSCAI parameter, is sent from the SMF 40 to the AMF 20. As will be described later, the domain number and the TSCAI parameter are transmitted as a list having “a set of domain number and TSCAI parameter” for each of one or more domain numbers. However, the sending in the form of a list is an example and it may be transmitted in a way other than the list.

N1N2MessageTransferReferqData includes N2InfoContainer as shown in 6.1.6.2.18 of Non-Patent Document 4 (TS29.518). As shown in 6.1.6.2.15, N2InfoContainer includes N2SmInformation. As shown in 6.1.6.2.26, N2SmInformation includes N2InfoContent. As shown in 6.1.6.2.27, N2InfoContent includes ngapData.

In addition, as shown in 6.1.6.4.3.2, there is a description to refer to Non-Patent Document 5 (TS38.413) regarding PDU Session Resource Setup Request Transfer IE, PDU Session Resource Request Transfer IE, etc., which is the content of NGAP IE. The operation of this embodiment follows Non-Patent Document 4 (T529.518) and the specification modified from Non-Patent Document 5 (TS38.413).

FIGS. 27 to 31 show a modification example 1 from Non-Patent Document 5 (abstract of T538.413). FIG. 27 shows a changed part of 8.2.1.2 Successful Operatio of the PDU session resource setup performed between the AMF 20 and the RAN 30. In the PDU Session Resource Setup Request sent from the AMF 20 to the RAN 30, the RAN 30 must consider the Traffic Characteristics list IE if the Traffic Characteristics list IE is included in the PDU Session Resource Setup Request Transfer IE of the PDU SESSION RESOURCE SETUP REQUEST message for each QoS flow requesting setup.

FIG. 28 shows a changed part of 8.2.3.2 Successful Operation of the PDU session resource modify performed between the AMF 20 and the RAN 30. In the PDU Session Resource Modification Request sent from the AMF 20 to the RAN 30, if the Traffic Characteristics list IE is included in the PDU Session Resource Request Transfer IE of the PDU SESSION RESOURCE MODIFY REQUEST message, the RAN 30 must consider the Traffic Characteristics list IE.

FIG. 29 shows details of the PDU Session Resource Setup Request Transfer IE in which a Traffic Characteristics list is added. The Traffic Characteristics list has pairs of Time Domain identifier and Traffic Characteristic for the number of time domains per QoS. FIG. 30 (PDU Session Resource Modify Request Transfer IE) is similar to that. FIG. 31 shows details of Time Domain Identifier and Traffic Characteristic.

FIGS. 32-33 show a modification example 2 from Non-Patent Document 5 (abstract of T538.413). FIG. 32 shows that TSC Assistance Information List, including TSC Assistance Information for each time domain, is included in the GBR QoS Flow Information sent from the AMF 20 to the RAN 30. FIG. 33 shows details of TSC Assistance Information and Time Domain Identifier.

FIGS. 34-36 show examples of modifications from Non-Patent Document 6 (extract of T538.415). As described in FIG. 34, DL PDU SESSION INFORMATION frame may contain a Time Domain Identifier (TDI) field in this embodiment. The RAN 30 can identify a TSN time domain to which a received packet belongs by TDI. FIG. 35 shows the DL PDU SESSION INFORMATION (PDU Type 0) format. FIG. 36 shows details of the Time Domain Identifier (TDI).

The modifications shown in FIGS. 34 to 36 are not mandatory. Even without the modification shown in FIGS. 34-36, the RAN 30 can understand the Burst Arrival Time or the like for each TSN time domain based on the TSCAI for each TSN time domain, so that packets can be processed for each TSN time domain.

As described above, according to the present Example, assistance information for time sensitive communication can be applied only to a specific TSN time domain.

(Equipment Configuration)

Next, a functional configuration example of the base station apparatus 30 corresponding to the RAN 30, the access mobile management apparatus 20 corresponding to the AMF 20, the session management apparatus 40 corresponding to the SMF 40, and the user plane apparatus 50 corresponding to the UPF 50 will be described.

<Base Station Apparatus 30>

FIG. 37 is a diagram illustrating an example of a functional configuration of the base station apparatus 30. As shown in FIG. 37, the base station apparatus 30 includes a transmission unit 310, a reception unit 320, a setting unit 330, and a control unit 340. The functional configuration shown in FIG. 37 is only one example. If the operation according to the embodiments of the present invention can be performed, the functional category and the name of the functional unit may be any one.

The transmission unit 310 includes a function for generating a signal to be transmitted and transmitting the signal to a terminal side (Uu side) and a core network side. The reception unit 320 includes a function for receiving various signals from the terminal side (Uu side) and the core network side and acquiring, for example, information of a higher layer from the received signals. The transmission unit 310 and the reception unit 320 may be referred to as a transmitter and a receiver, respectively.

The setting unit 330 stores configuration information in the storage device (storage unit) and reads the configuration information from the storage device as necessary. The control unit 340 controls the base station apparatus 30.

For example, the reception unit 320 receives a message including TSC assistance information and identification information of the TSN time domain to which the TSC assistance information is to be applied from the network apparatus, and the transmission unit 310 transmits data based on the TSC assistance information.

<Access Mobility Management Apparatus 20>

FIG. 38 is a diagram illustrating an example of a functional configuration of an access mobile management apparatus 20. As shown in FIG. 38, the access mobile management apparatus 20 includes a transmission unit 210, a reception unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in FIG. 38 is only one example. If the operation according to the embodiments of the present invention can be performed, the functional category and the name of the functional unit may be any one.

The transmission unit 210 includes a function for generating a signal to be transmitted and transmitting the signal to a network. The reception unit 220 includes a function for receiving various signals and acquiring, for example, information of a higher layer from the received signals. The transmission unit 210 and the reception unit 220 may be called a transmitter and a receiver, respectively.

The setting unit 230 stores configuration information in the storage device (storage unit) and reads the configuration information from the storage device as necessary. The control unit 240 controls the access mobile management apparatus 20.

<Session Management Apparatus 40>

FIG. 39 is a diagram illustrating an example of a functional configuration of the session management apparatus 40. As shown in FIG. 39, the session management apparatus 40 includes a transmission unit 410, a reception unit 420, a setting unit 430, and a control unit 440. The functional configuration shown in FIG. 39 is only one example. If the operation according to the embodiments of the present invention can be performed, the functional category and the name of the functional unit may be any one.

The transmission unit 410 includes a function for generating a signal to be transmitted and transmitting the signal to a network. The reception unit 420 includes a function for receiving various signals and acquiring, for example, information of a higher layer from the received signals. The transmitting unit 410 and the receiving unit 420 may be referred to as a transmitter and a receiver, respectively.

The setting unit 430 stores configuration information in the storage device (storage unit) and reads the configuration information from the storage device as necessary. The control unit 440 controls the session management apparatus 40.

<User Plane Apparatus 50>

FIG. 40 is a diagram illustrating an example of the functional configuration of the user plane apparatus 50. As shown in FIG. 40, the user plane apparatus 50 includes a transmission unit 510, a reception unit 520, a setting unit 530, and a control unit 540. The functional configuration shown in FIG. 40 is only one example. If the operation according to the embodiments of the present invention can be performed, the functional category and the name of the functional unit may be any one.

The transmission unit 510 includes a function for generating a signal to be transmitted and transmitting the signal to a network. The reception unit 520 includes a function for receiving various signals and acquiring, for example, information of a higher layer from the received signals. The transmission unit 510 and the reception unit 520 may be referred to as a transmitter and a receiver, respectively.

The setting unit 530 stores configuration information in the storage device (storage unit) and reads the configuration information from the storage device as necessary. The control unit 540 controls the user plane apparatus 50.

(Hardware Configuration)

Block diagrams (FIGS. 37-40) used for the description of the above embodiments show blocks of functional units. These functional blocks (components) are implemented by any combination of hardware and/or software. In addition, the implementation method of each function block is not particularly limited. That is, each functional block may be implemented using a single device that is physically or logically combined, or two or more devices that are physically or logically separated may be directly or indirectly connected (e.g., using wired, wireless, etc.) and implemented using these multiple devices. The functional block may be implemented by combining software with the device or devices.

Functions include, but are not limited to, judgment, determination, determination, calculation, calculation, processing, derivation, research, search, verification, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, and deeming; broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, a functional block (component) that functions to transmit is called a transmitting unit or a transmitter. In either case, as described above, the realization method is not particularly limited.

For example, the base station apparatus 30, the access mobile management apparatus 20, the session management apparatus 40, the user plane apparatus 50, and the like according to an embodiment of the present disclosure may function as a computer for processing the present disclosure. FIG. 41 is a diagram illustrating an example of a hardware configuration such as a base station apparatus 30, an access mobile management apparatus 20, a session management apparatus 40, and a user plane apparatus 50 according to an embodiment of the present disclosure. The base station apparatus 30, the access mobile management apparatus 20, the session management apparatus 40, and the user plane apparatus 50 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. The base station apparatus 30, the access mobile management apparatus 20, the session management apparatus 40, the user plane apparatus 50, or the like may be virtual machines.

In the following description, the term “apparatus” can be read as circuits, devices, units, etc. The hardware configuration of the base station apparatus 30, the access mobile management apparatus 20, the session management apparatus 40, and the user plane apparatus 50 may be configured to include one or more of the devices shown in the figure or may be configured without some of the devices.

The functions of the base station apparatus 30, the access mobile management apparatus 20, the session management apparatus 40, and the user plane apparatus 50 are realized by performing an operation by the processor 1001 by reading predetermined software (programs) on hardware such as the processor 1001, the storage device 1002, or the like, and controlling communication by the communication device 1004 or reading and/or writing data in the storage device 1002 and the auxiliary storage device 1003.

Processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be comprised of a central processing unit (CPU) including an interface with peripheral devices, a controller, an arithmetic unit, a register, and the like. For example, the above-described control portion 340, control portion 440, control portion 540, and the like may be implemented by the processor 1001.

The processor 1001 reads out a program (program code), software module, data, or the like from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002 and performs various processing in accordance with the above. As a program, a program that causes a computer to execute at least a part of the operation described in the above-described embodiment is used. For example, the control portion of each device may be stored in the storage device 1002 and implemented by a control program operating in the processor 1001. Although the foregoing processes have been described and executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. Processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunication line.

The storage device 1002 is a computer-readable recording medium and may be constituted by at least one of, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), and the like. The storage device 1002 may also be referred to as a register, a cache, a main memory (main storage device), or the like. The storage device 1002 can store a program (program code), a software module and the like that can be executed to perform a communication method according to an embodiment of the present disclosure.

The auxiliary storage device 1003 is a computer-readable recording medium and may be configured by at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, or a Blu-ray (registered trademark) disk), a smart card, a flash memory (for example, a card, a stick, or a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. The auxiliary storage device 1003 may be referred to as an auxiliary storage device. The above storage medium may be, for example, a database, a server, or other appropriate media including at least one of the storage device 1002 and the auxiliary storage device 1003.

The communication device 1004 is hardware (a transmission and reception device) for performing communication between computers through at least one of a wired and wireless networks and may also be referred to as, for example, a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 may include, for example, a radio frequency switch, a duplexer, a filter, a frequency synthesizer, or the like to implement at least one of a frequency division duplex (FDD) and a time division duplex (TDD). For example, a transmission and reception antenna, an amplifier, a transmitting and receiving unit, a transmission line interface, and the like may be implemented by the communication device 1004. The transmitting and receiving unit may be implemented in such a manner that a transmitting unit and a receiving unit are physically or logically separated.

The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or the like) that receives an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, or the like) that performs an output to the outside. It is noted that the input device 1005 and the output device 1006 may be integrated with each other (for example, a touch panel).

The devices, such as the processor 1001 and the storage device 1002, are connected to each other via a bus 1007 for communicating information. The bus 1007 may be constituted by using a single bus, or may be constituted by using busses different depending on devices.

The base station apparatus 30, the access mobility management apparatus 20, the session management apparatus 40 and the user plane apparatus 50 may include hardware, such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), or alternatively, some or all of the functional blocks may be implemented by the hardware. For example, the processor 1001 may be implemented with at least one of these hardware components.

SUMMARY OF EMBODIMENTS

According to the present embodiment, at least the session management apparatus, the user plane apparatus, and the access mobile management apparatus shown in the following items 1 to 5 are provided.

(Item 1)

1. A session management apparatus comprising:

a reception unit configured to receive, from a user plane apparatus, a time offset between a TSN time of a TSN time domain and a 5G time, and identification information of the TSN time domain; and

a transmission unit configured to transmit, to a base station apparatus, a TSC assistance information determined based on the time offset and the identification information of the TSN time domain.

(Item 2)

2. The session management apparatus as described in item 1, wherein, when the user plane apparatus detects a drift between the TSN time of the TSN time domain and the 5G time, the reception unit receives the time offset and the identification information of the TSN time domain.

(Item 3)

3. A user plain apparatus comprising:

a control unit configured to detect a drift between a TSN time of a TSN time domain and a 5G time; and

a transmission unit configured, when the drift is detected, to transmit, to a session management apparatus, a time offset between the TSN time of the TSN time domain and the 5G time, and identification information of the TSN time domain.

(Item 4)

4. An access mobile management apparatus comprising:

a reception unit configured to receive, from a session management apparatus, a TSC assistance information, and identification information of a TSN time domain to be applied to the TSC assistance information; and

a transmission unit configured to transmit, to a base station apparatus, the TSC assistance information, and the identification information of the TSN time domain to be applied to the TSC assistance information.

(Item 5)

5. The access mobile management apparatus as described in item 4, wherein the transmission unit transmits, to the base station apparatus, a message including a list that includes, for each of one or more TSN time domains, TSC assistance information and identification information of a TSN time domain to which the TSC assistance information should be applied.

According to any item of 1 to 5, there is provided a technique that allows TSC assistance information to be applied only to a specific TSN time domain.

Supplements to Embodiment

The embodiment of the present invention has been described above, but the disclosed invention is not limited to the above embodiment, and those skilled in the art would understand that various modified examples, revised examples, alternative examples, substitution examples, and the like can be made. In order to facilitate understanding of the present invention, specific numerical value examples are used for explanation, but the numerical values are merely examples, and any suitable values may be used unless otherwise stated. Classifications of items in the above description are not essential to the present invention, contents described in two or more items may be used in combination if necessary, and contents described in an item may be applied to contents described in another item (unless a contradiction arises). The boundaries between the functional units or the processing units in the functional block diagrams do not necessarily correspond to the boundaries of physical components. Operations of a plurality of functional units may be physically implemented by a single component and an operation of a single functional unit may be physically implemented by a plurality of components. Concerning the processing procedures described above in the embodiment, the orders of steps may be changed unless a contradiction arises. For the sake of convenience for describing the processing, the base station apparatus 30, the access mobility management apparatus 20, the session management apparatus 40 and the user plane apparatus 50 have been described with the use of the functional block diagrams, but these apparatuses may be implemented by hardware, software, or a combination thereof. Each of software functioning with a processor of each apparatus according to the embodiment of the present invention may be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an EPROM, an EEPROM, a register, a hard disk (HDD), a removable disk, a CD-ROM, a database, a server, or any suitable recording media.

Also, the notification of information is not limited to the aspect or embodiment described in the present disclosure, but may be performed by other methods. For example, the notification of information may be performed by physical layer signaling (for example, DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (an MIB (Master Information Block) and an SIB (System Information Block)), other signals, or combinations thereof. The RRC signaling may be also be referred to as an RRC message and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

Each aspect and embodiment described in the present disclosure may be applied to at least one of a system that uses a suitable system such as LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), or Bluetooth (registered trademark), and a next-generation system expanded on the basis thereof. Also a plurality of systems may be combined and applied (for example, a combination of at least one of LTE and LTE-A with 5G, and the like).

In the operation procedures, sequences, flowcharts, and the like according to each aspect and embodiment described in the present disclosure, the orders of steps may be changed unless a contradiction arises. For example, in the methods described in the present disclosure, elements of various steps are illustrated by using an exemplary order and the methods are not limited to the specific orders presented.

The specific operations performed by the base station apparatus 30, the access mobility management apparatus 20, the session management apparatus 40 and the user plane apparatus 50 and the like described in the present disclosure may in some cases be performed by another node.

Information, signals, or the like described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). Information, signals, or the like described in the present disclosure may be input and output via a plurality of network nodes.

Information or the like that has been input or output may be stored at a predetermined place (for example, a memory) and may be managed with the use of a management table. Information or the like that is input or output can be overwritten, updated, or appended. Information or the like that has been output may be deleted. Information or the like that has been input may be transmitted to another apparatus.

In the present disclosure, determination may be made with the use of a value expressed by one bit (0 or 1), may be made with the use of a Boolean value (true or false), and may be made through a comparison of numerical values (for example, a comparison with a predetermined value).

Regardless of whether software is referred to as software, firmware, middleware, microcode, a hardware description language, or another name, software should be interpreted broadly to mean instructions, instruction sets, codes, code segments, program codes, a program, a sub-program, a software module, an application, a software application, a software package, a routine, a subroutine, an object, an executable file, an execution thread, a procedure, a function, and the like.

Software, instructions, information, or the like may be transmitted and received through transmission media. For example, in a case where software is transmitted from a website, a server or another remote source through at least one of wired technology (such as a coaxial cable, an optical-fiber cable, a twisted pair, or a digital subscriber line (DSL)) and radio technology (such as infrared or microwaves), at least one of the wired technology and the radio technology is included in the definition of a transmission medium.

Information, signals, and the like described in the present disclosure may be expressed with the use of any one of various different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, and the like mentioned herein throughout the above explanation may be expressed by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combinations thereof.

The terms described in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). A signal may be a message. A component carrier (CC) may be referred to as a carrier frequency, a cell, a frequency carrier, or the like.

The terms “system” and “network” used in the present disclosure are used interchangeably.

Information, parameters, and the like described in the present disclosure may be expressed by absolute values, may be expressed by relative values with respect to predetermined values, and may be expressed by corresponding different information. For example, radio resources may be indicated by indexes.

The above-described names used for the parameters are not restrictive in any respect. In addition, formulas or the like using these parameters may be different from those explicitly disclosed in the present disclosure. Various channels (for example, a PUSCH, a PUCCH, a PDCCH, and the like) and information elements can be identified by any suitable names, and therefore, various names given to these various channels and information elements are not restrictive in any respect.

In the present disclosure, terms such as “base station (BS)”, “radio base station”, “base station apparatus”, “fixed station”, “NodeB”, “eNodeB (eNB)”, “gNodeB (gNB)”, “access point”, “transmission point”, “reception point”, “transmission/reception point”, “cell”, “sector”, “cell group”, “carrier”, “component carrier”, and the like may be used interchangeably. A base station may be referred to as a macro-cell, a small cell, a femtocell, a pico-cell, or the like.

A base station can accommodate one or a plurality of (for example, three) cells (that may be called sectors). In a case where a base station accommodates a plurality of cells, the whole coverage area of the base station can be divided into a plurality of smaller areas. For each smaller area, a base station subsystem (for example, an indoor miniature base station RRH (Remote Radio Head)) can provide a communication service. The term “cell” or “sector” denotes all or a part of the coverage area of at least one of a base station and a base station subsystem that provides communication services in the coverage.

In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” may be used interchangeably.

By the person skilled in the art, a mobile station may be referred to as any one of a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, and other suitable terms.

At least one of a base station and a mobile station may be referred to as a transmitting apparatus, a receiving apparatus, a communication apparatus, or the like. At least one of a base station and a mobile station may be an apparatus mounted on a mobile body, or may be a mobile body itself, or the like. A mobile body may be a transporting device (e.g., a vehicle, an airplane, and the like), an unmanned mobile (e.g., a drone, an automated vehicle, and the like), or a robot (of a manned or unmanned type). It is noted that at least one of a base station and a mobile station includes an apparatus that does not necessarily move during a communication operation. For example, at least one of a base station and a mobile station may be an IoT (Internet of Thing) device such as a sensor.

The term “determine” used herein may mean various operations. For example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (for example, looking up a table, a database, or another data structure), ascertaining, or the like may be deemed as making determination. Also, receiving (for example, receiving information), transmitting (for example, transmitting information), inputting, outputting, or accessing (for example, accessing data in a memory), or the like may be deemed as making determination. Also, resolving, selecting, choosing, establishing, comparing, or the like may be deemed as making determination. That is, doing a certain operation may be deemed as making determination. “To determine” may be read as “to assume”, “to expect”, “to consider”, or the like.

Each of the terms “connected” and “coupled” and any variations thereof mean any connection or coupling among two or more elements directly or indirectly and can mean that one or a plurality of intermediate elements are inserted among two or more elements that are “connected” or “coupled” together. Coupling or connecting among elements may be physical one, may be logical one, and may be a combination thereof. For example, “connecting” may be read as “accessing”. In a case where the terms “connected” and “coupled” and any variations thereof are used in the present disclosure, it may be considered that two elements are “connected” or “coupled” together with the use of at least one type of a medium from among one or a plurality of wires, cables, and printed conductive traces, and in addition, as some non-limiting and non-inclusive examples, it may be considered that two elements are “connected” or “coupled” together with the use of electromagnetic energy such as electromagnetic energy having a wavelength of the radio frequency range, the microwave range, or the light range (including both of the visible light range and the invisible light range).

A reference signal can be abbreviated as an RS (Reference Signal). A reference signal may be referred to as a pilot depending on an applied standard.

A term “based on” used in the present disclosure does not mean “based on only” unless otherwise specifically noted. In other words, a term “base on” means both “based on only” and “based on at least”.

Any references to elements denoted by a name including terms such as “first” or “second” used in the present disclosure do not generally limit the amount or the order of these elements. These terms can be used in the present disclosure as a convenient method for distinguishing one or a plurality of elements. Therefore, references to first and second elements do not mean that only the two elements can be employed or that the first element should be, in some way, prior to the second element.

“Means” in each of the above apparatuses may be replaced with “unit”, “circuit”, “device”, or the like.

In a case where any one of “include”, “including”, and variations thereof is used in the present disclosure, each of these terms is intended to be inclusive in the same way as the term “comprising”. Further, the term “or” used in the present disclosure is intended to be not exclusive-or.

A radio frame may include, in terms of time domain, one or a plurality of frames. Each of one or a plurality of frames may be referred to as a subframe in terms of time domain. A subframe may include, in terms of time domain, one or a plurality of slots. A subframe may have a fixed time length (e.g., 1 ms) independent of Numerology.

Numerology may be a communication parameter that is applied to at least one of transmission and reception of a signal or a channel. Numerology may mean, for example, at least one of a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame configuration, a specific filtering processing performed by a transceiver in frequency domain, a specific windowing processing performed by a transceiver in time domain, and the like.

A slot may include, in terms of time domain, one or a plurality of symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiplexing) symbols) symbols, or the like). A slot may be a time unit based on Numerology.

A slot may include a plurality of minislots. Each minislot may include one or a plurality of symbols in terms of the time domain. A minislot may also be referred to as a subslot. A minislot may include fewer symbols than a slot. A PDSCH (or PUSCH) transmitted at a time unit greater than a minislot may be referred to as a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using minislots may be referred to as a PDSCH (or PUSCH) mapping type B.

Each of a radio frame, a subframe, a slot, a minislot, and a symbol means a time unit configured to transmit a signal. Each of a radio frame, a subframe, a slot, a minislot, and a symbol may be referred to as other names respectively corresponding thereto.

For example, one subframe may be referred to as a transmission time interval (TTI), a plurality of consecutive subframes may be referred to as a TTI, and one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) according to the existing LTE, may have a period shorter than 1 ms (e.g., 1 to 13 symbols), and may have a period longer than 1 ms. Instead of subframes, units expressing a TTI may be referred to as slots, minislots, or the like.

A TTI means, for example, a minimum time unit of scheduling in radio communication. For example, in an LTE system, a base station performs scheduling for each user terminal 20 to assign, in TTI units, radio resources (such as frequency bandwidths, transmission power, and the like that can be used by each user terminal 20). However, the definition of a TTI is not limited thereto.

A TTI may be a transmission time unit for channel-coded data packets (transport blocks), code blocks, code words, or the like, and may be a unit of processing such as scheduling, link adaptation, or the like. When a TTI is given, an actual time interval (e.g., the number of symbols) to which transport blocks, code blocks, code words, or the like are mapped may be shorter than the given TTI.

In a case where one slot or one minislot is referred to as a TTI, one or a plurality of TTIs (i.e., one or a plurality of slots or one or a plurality of minislots) may be a minimum time unit of scheduling. The number of slots (the number of minislots) included in the minimum time unit of scheduling may be controlled.

A TTI having a time length of 1 ms may referred to as an ordinary TTI (a TTI according to LTE Rel.8-12), a normal TTI, a long TTI, an ordinary subframe, a normal subframe, a long subframe, a slot, or the like. A TTI shorter than an ordinary TTI may be referred to as a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, or the like.

Note that a long TTI (for example, normal TTI, subframe, and the like) may be read as TTI having a time length exceeding 1 ms, and a short TTI (for example, shortened TTI) may be read as a TTI having a TTI length less than the TTI length of the long TTI and equal to or more than 1 ms.

A resource block (RB) is a resource assignment unit in terms of time domain and frequency domain and may include one or a plurality of consecutive subcarriers in terms of frequency domain. The number of subcarriers included in an RB may be the same regardless of Numerology, and, for example, may be 12. The number of subcarriers included in a RB may be determined based on Numerology.

In terms of time domain, an RB may include one or a plurality of symbols, and may have a length of 1 minislot, 1 subframe, or 1 TTI. Each of 1 TTI, 1 subframe, and the like may include one or a plurality of resource blocks.

One or a plurality of RBs may be referred to as physical resource blocks (PRBs: Physical RBs), a subcarrier group (SCG: Sub-Carrier Group), a resource element group (REG: Resource Element Group), a PRB pair, an RB pair, or the like.

A resource block may include one or a plurality of resource elements (RE: Resource Elements). For example, 1 RE may be a radio resource area of 1 subcarrier and 1 symbol.

A bandwidth part (BWP) (which may be called a partial bandwidth or the like) may mean a subset of consecutive common RBs (common resource blocks) for Numerology, in any given carrier. A common RB may be identified by a RB index with respect to a common reference point in the carrier. PRBs may be defined by a BWP and may be numbered in the BWP.

A BWP may include a BWP (UL BWP) for UL and a BWP (DL BWP) for DL. For a UE, one or a plurality of BWPs may be set in 1 carrier.

At least one of BWPs that have been set may be active, and a UE need not assume sending or receiving a predetermined signal or channel outside the active BWP. A “cell”, a “carrier” or the like in the present disclosure may be read as a “BWP”.

The above-described structures of radio frames, subframes, slots, minislots, symbols, and the like are merely examples. For example, the number of subframes included in a radio frame, the number of slots included in a subframe or a radio frame, the number of minislots included in a slot, the number of symbols and the number of RBs included in a slot or a minislot, the number of subcarriers included in an RB, the number of symbols included in a TTI, a symbol length, a cyclic prefix (CP) length, and the like can be variously changed.

Throughout the present disclosure, in a case where an article such as “a”, “an”, or “the” in English is added through a translation, the present disclosure may include a case where a noun following such article is of a plural forms.

Throughout the present disclosure, an expression that “A and B are different” may mean that “A and B are different from each other”. Also this term may mean that “each of A and B is different from C”. Terms such as “separate” and “coupled” may also be interpreted in a manner similar to “different”.

Each aspect or embodiment described in the present disclosure may be solely used, may be used in combination with another embodiment, and may be used in a manner of being switched with another embodiment upon implementation. Notification of predetermined information (for example, notification of “being x”) may be implemented not only explicitly but also implicitly (for example, by not notifying predetermined information).

Although the present disclosure has been described above, it will be understood by those skilled in the art that the present disclosure is not limited to the embodiment described in the present disclosure. Modifications and changes of the present disclosure may be possible without departing from the subject matter and the scope of the present disclosure defined by claims. Therefore, the descriptions of the present disclosure are for illustrative purposes only, and are not intended to be limiting the present disclosure in any way.

DESCRIPTION OF SYMBOLS

-   20 Access mobile control apparatus -   210 Transmission unit -   220 Reception unit -   230 Setting unit -   240 Control unit -   30 Session management apparatus -   310 Transmission unit -   320 Reception unit -   330 Setting part -   340 Control unit -   40 Session management apparatus -   410 Transmission unit -   420 Reception unit -   430 Setting unit -   440 Controller -   50 User plane apparatus -   510 Transmission unit -   520 Reception unit -   530 Setting unit -   540 Control unit -   1001 Processor -   1002 Storage memory -   1003 Auxiliary store -   1004 Communication device -   1005 Input device -   1006 Output device 

1. A session management apparatus comprising: a reception unit configured to receive, from a user plane apparatus, a time offset between a TSN time of a TSN time domain and a 5G time, and identification information of the TSN time domain; and a transmission unit configured to transmit, to a base station apparatus, a TSC assistance information determined based on the time offset and the identification information of the TSN time domain.
 2. The session management apparatus as claimed in claim 1, wherein, when the user plane apparatus detects a drift between the TSN time of the TSN time domain and the 5G time, the reception unit receives the time offset and the identification information of the TSN time domain.
 3. A user plain apparatus comprising: a control unit configured to detect a drift between a TSN time of a TSN time domain and a 5G time; and a transmission unit configured, when the drift is detected, to transmit, to a session management apparatus, a time offset between the TSN time of the TSN time domain and the 5G time, and identification information of the TSN time domain.
 4. An access mobile management apparatus comprising: a reception unit configured to receive, from a session management apparatus, a TSC assistance information, and identification information of a TSN time domain to be applied to the TSC assistance information; and a transmission unit configured to transmit, to a base station apparatus, the TSC assistance information, and the identification information of the TSN time domain to be applied to the TSC assistance information.
 5. The access mobile management apparatus as claimed in claim 4, wherein the transmission unit transmits, to the base station apparatus, a message including a list that includes, for each of one or more TSN time domains, TSC assistance information and identification information of a TSN time domain to which the TSC assistance information should be applied. 